See Slack thread for background.

There was a bug in the install.sh script, where if you were currently running the tiger binary (most commonly when running the MCP server via an AI tool like Claude Code), then when the script swapped it out for the new binary, the operating system would immediately kill future invocations of the command until all of the existing invocations of the old binary were finished running. This PR fixes it by first removing the old binary with rm -f before swapping the new binary into place (fwiw, I don't fully understand what the underlying issue is or why this fixes it, but it does, based on my testing).

Closes AGE-209

How to Test

1. Install the CLI via the install.sh script if you haven't already: sh ./scripts/install.sh
   • Make sure the first tiger command in your $PATH is the one installed via the script: which tiger (should print ~/.local/bin/tiger or ~/bin/tiger). If it's not, uninstall the other binaries or update your $PATH.
2. Install the MCP server into Claude Code: tiger mcp install claude-code
3. Open Claude Code in a separate terminal and leave it running: claude.
4. Run the install script to install a new version of the binary: sh ./scripts/install.sh
5. Run tiger version

Previously, the last step (running tiger version) would fail immediately with an error saying it had been killed (you could fix it either by closing the Claude Code session, or manually removing the binary and re-installing). After this PR, the command should execute like normal.